release: chdb 3.0.0 on chdb-core v26.5.0#45
Merged
Conversation
Stable release on the v26.5.0 engine line. Pins the per-platform native subpackages to exact 26.5.0 (was the >=26.5.0 range) so a 3.0.0 install always resolves the 26.5.0 engine instead of floating onto a newer subpackage. The raw/streaming insert API is intentionally NOT in this release — it requires the written-rows accessors added to chdb-core after v26.5.0, and ships separately on the v26.5.1 line. Full v3 suite green against v26.5.0 (118 passed). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Cuts the stable
chdb@3.0.0release on the chdb-core v26.5.0 engine line. Single-file change topackage.json:version2.0.0 → 3.0.0optionalDependenciesfor the four@chdb/lib-*native subpackages:>=26.5.0→ exact26.5.0.update_libchdb.shalready points atv26.5.0onmain; no change needed.Why pin the subpackages exactly
The
>=26.5.0range would let achdb@3.0.0install float onto a newer engine subpackage (e.g. a future26.5.1) — a stable release should resolve a fixed, tested engine. Exact26.5.0guarantees reproducible installs.Test
npm run test:v3green against v26.5.0: 118 passed. (The legacy mochatest/test:allruns on CI's Node 22.x; it trips a yargs/ESM error only on very new local Node, unrelated to this change.)Release (separate, gated step)
Publishing happens on a pushed
v3.0.0tag (→ npm dist-taglatest), not on merge. To be done after this merges.